feat: F5 dos for nginx 4.9 by rnitzan · Pull Request #1863 · nginx/documentation

rnitzan · 2026-04-19T09:05:06Z

Proposed changes

F5 Dos for NGINX v4.9 release over NGINX Plus R37

Align with NGINX Plus R37
Adding RHEL 10 support
Adding Debian 13 support
Docker and k8s documentation update

Checklist

Before sharing this pull request, I completed the following checklist:

I read the Contributing guidelines
My branch adheres to the Git conventions
My content changes adhere to the F5 NGINX Documentation style guide
If my changes involve potentially sensitive information¹, I have assessed the possible impact
I have waited to ensure my changes pass tests, and addressed any discovered issues

Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

github-actions · 2026-04-19T09:13:19Z

✅ Deploy Preview will be available once build job completes!

Name	Link
😎 Deploy Preview	https://frontdoor-test-docs.nginx.com/previews/docs/1863/

…ent (#1871) * added Google site verification file for Google Search Console enablement * moved to /static --------- Co-authored-by: Lam Nguyen <la.nguyen@f5.com>

) * Add instructions that shows a user how update an existing license * Minor change to kubectl param * Correct param

…r security monitoring (#1861) * docs(nginx-one): improve security monitoring setup verification - Clarify where to place the secops_dashboard logging directives in the NGINX configuration and expand the verification flow into a concrete end-to-end check using the Security Dashboard Event Logs tab. - Add labeled example test requests for common attack patterns (XSS, path traversal, SQL injection) so operators can generate sample security events while setting up the default blocking policy. Document that customized or transparent policies may alert instead of block. * docs(nginx-one): add local security monitoring troubleshooting guide - Add a new local data plane troubleshooting guide for NGINX One security monitoring to help customers diagnose why F5 WAF for NGINX security events do not appear in the dashboard after setup. - The new guide covers four checks: - invalid secops_dashboard log profile errors in the embedded collector log - port 1514 ownership for local syslog delivery - presence of the generated security log pipeline in the collector config - optional debug exporter configuration for collector-side verification Also update the main security monitoring setup guide to improve verification, add labeled example attack requests for generating test events, and link to the new troubleshooting workflow. Update the section landing page so the new guide is discoverable from the security monitoring docs. * Update content/nginx-one-console/waf-integration/waf-security-dashboard/local-dataplane-troubleshooting.md Update as recommended Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> --------- Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com>

JTorreG · 2026-04-30T14:08:00Z

@@ -0,0 +1,57 @@
+---
+nd-docs: null


Suggested change

nd-docs: null

Why null?
Please either leave this line out or use the placeholder docs-000. Don't come up with new interesting ways to fill up this value that might confuse our automations

JTorreG · 2026-04-30T14:12:08Z

+---
+# We use sentence case and present imperative tone
+title: "Kubernetes"
+# Weights are assigned in increments of 100: determines sorting order
+weight: 100
+# Creates a table of contents and sidebar, useful for large documents
+toc: true
+# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
+nd-content-type: how-to
+nd-product: F5DOSN
+---


Please follow the template here. Add the missing values for keywords, summary, and audience.

JTorreG · 2026-04-30T14:13:20Z

+---
+## F5 DoS for NGINX Arbitrator


Suggested change

---

## F5 DoS for NGINX Arbitrator

---

## F5 DoS for NGINX Arbitrator

JTorreG · 2026-04-30T14:17:51Z

+---
+---


here and in all the new files in the includes/dos folder

Includes must indicate in which files the content is being used with the nd-files key
Includes must indicate the product using the nd-product key ( F5DOSN)

General question on the scripts. None of them will work unless you've set up admin privileges (such as with sudo). I don't see any evidence that you've set up sudo with any of the includes.

JTorreG · 2026-04-30T14:18:28Z

@@ -0,0 +1,24 @@
+---
+nd-docs: null


Suggested change

nd-docs: null

JTorreG · 2026-04-30T14:18:37Z

@@ -0,0 +1,26 @@
+---
+nd-docs: null


Suggested change

nd-docs: null

JTorreG · 2026-04-30T14:18:46Z

@@ -0,0 +1,91 @@
+---
+nd-docs: null


Suggested change

nd-docs: null

JTorreG · 2026-04-30T14:19:44Z

+
+## Use Helm to install F5 DOS for NGINX
+
+You will need to edit the `values.yaml` file for a few changes:


Suggested change

You will need to edit the `values.yaml` file for a few changes:

To use Helm to install F5 DOS for NGINX you need to edit the `values.yaml` and apply the following changes:

JTorreG · 2026-04-30T14:20:22Z

+
+- Update _appprotectdos.image.repository_ and _appprotectdos.image.tag_  with the image name chosen during when [building the Docker image](#build-the-docker-image).
+
+The `<JWT Token>` argument should be the _contents_ of the file, not the file itself. Ensure there are no additional characters such as extra whitespace.


Suggested change

The `<JWT Token>` argument should be the _contents_ of the file, not the file itself. Ensure there are no additional characters such as extra whitespace.

The `<JWT Token>` argument must be the _contents_ of the file, not the file itself. Ensure there are no additional characters such as extra whitespace.

should is vague. Avoid.

JTorreG · 2026-04-30T14:20:45Z

+  -t <your-nginx-dos-image-name> .
+```
+
+Once you have built the image, push it to your private image repository, which should be accessible to your Kubernetes cluster.


Suggested change

Once you have built the image, push it to your private image repository, which should be accessible to your Kubernetes cluster.

Once you have built the image, push it to your private image repository, which must be accessible to your Kubernetes cluster.

JTorreG · 2026-04-30T14:21:48Z

+
+## Create a Dockerfile
+
+In the same folder as your credential files, create a _Dockerfile_ based on your desired operating system image using an example from the following sections.


Suggested change

In the same folder as your credential files, create a _Dockerfile_ based on your desired operating system image using an example from the following sections.

Create a _Dockerfile_ based on your desired operating system image in the same folder as your credential files using an example from the following sections.

JTorreG · 2026-04-30T14:25:00Z

+
+The `<JWT Token>` argument should be the _contents_ of the file, not the file itself. Ensure there are no additional characters such as extra whitespace.
+
+On helm deployment environment variables need to be set for image repository and tag.


Suggested change

On helm deployment environment variables need to be set for image repository and tag.

On Helm, set the deployment environment variables for image repository and tag.

JTorreG · 2026-04-30T14:25:27Z

+`set enviorment variable DOS_IMAGE_REPOSITORY` with your actual nginx-dos image anmae.
+`set enviorment variable DOS_IMAGE_TAG` with your actual nginx-dos image tag.


Suggested change

`set enviorment variable DOS_IMAGE_REPOSITORY` with your actual nginx-dos image anmae.

`set enviorment variable DOS_IMAGE_TAG` with your actual nginx-dos image tag.

`set environment variable DOS_IMAGE_REPOSITORY` with your actual nginx-dos image anmae.

`set environment variable DOS_IMAGE_TAG` with your actual nginx-dos image tag.

this step is unclear to me. I think it needs to be explained with more detail.

Check the how-to template for guidance on how we use placeholders in the docs.

JTorreG · 2026-04-30T14:28:20Z

+
+{{< call-out "note" >}}
+
+At this stage, you have finished deploying F5 DOS for NGINX and can look at [Post-installation checks](#post-installation-checks).


Suggested change

At this stage, you have finished deploying F5 DOS for NGINX and can look at [Post-installation checks](#post-installation-checks).

The deployment of F5 DOS for NGINX is now complete. You can skip to the [Post-installation checks](#post-installation-checks) now.

JTorreG · 2026-04-30T14:28:56Z

+On manifest deployment environment variables need to be set for image repository and tag.
+`set enviorment variable DOS_IMAGE_REPOSITORY` with your actual nginx-dos image anmae.
+`set enviorment variable DOS_IMAGE_TAG` with your actual nginx-dos image tag.


see my comment and fixes in the previous section

JTorreG · 2026-04-30T14:29:27Z

+NAME                TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
+nap-dos             LoadBalancer   10.43.83.225    <pending>     80:30307/TCP   1m
+```
+## Post-Installation Checks


Suggested change

## Post-Installation Checks

## Post-installation checks

Sentence case capitalization

JTorreG · 2026-04-30T14:30:26Z

+and can look at .
+{{< include "dos/install-post-checks.md" >}}
+
+## F5 DoS for NGINX Arbitrator


Suggested change

## F5 DoS for NGINX Arbitrator

## F5 DoS for NGINX arbitrator

Sentence case

JTorreG · 2026-04-30T14:33:09Z

+---
+nd-content-type: how-to
+nd-docs: DOCS-000
+nd-product: NONECO
+title: Troubleshoot security monitoring on the local data plane
+description: "Check the local NGINX Agent and OpenTelemetry Collector configuration when F5 WAF for NGINX security events do not appear in NGINX One Console."
+weight: 450
+toc: true
+nd-keywords: "security monitoring, troubleshooting, local data plane, nginx-agent, opentelemetry collector, secops_dashboard, WAF events"
+nd-summary: >
+  Use this guide when F5 WAF for NGINX security events do not appear in the NGINX One Console security dashboard even after you complete the setup flow.
+  It walks through the local data plane checks for invalid log profiles, missing OpenTelemetry log pipelines, and debug logging.
+  These checks help confirm whether NGINX Agent is receiving, parsing, and forwarding security events correctly.
+nd-audience: operator
+---
+


We strongly advise not to create specific documents for troubleshooting.

Troubleshooting advice should be either live next to the how-to/tutorial steps that can cause the issues, or in the myF5 KB.

Please review this document and decide if the guidance provide here can live next to the steps it's trying to troubleshoot in other docs.

JTorreG · 2026-04-30T14:36:29Z

@@ -0,0 +1 @@
+google-site-verification: google1f145127a2762dc1.html


what is the purpose of this?

This file was added in a separate PR (to enable Google Search Console). I think this PR just needs to merge in changes from main -- it seems behind.

See: #1871

JTorreG

Please review the suggestions and comments. there are major issues in this PR that must be resolved before merge

JTorreG · 2026-04-30T14:39:58Z

@rnitzan on top of 2 technical writer approvals for the prose content, we will also need a review and approval from an engineer to confirm that all the dockerfiles have been tested and are correct. Thank you.

mjang · 2026-04-30T15:52:57Z

+---
+---


General question on the scripts. None of them will work unless you've set up admin privileges (such as with sudo). I don't see any evidence that you've set up sudo with any of the includes.

… release

… for 4.9 release" This reverts commit dab3055.

travisamartin · 2026-04-30T22:31:32Z

This include isn't actually used anywhere.

travisamartin · 2026-04-30T22:31:52Z

This include isn't actually used anywhere.

travisamartin · 2026-04-30T22:33:04Z

@rnitzan -- I opened a PR w/ my suggested edits. Take a look: #1905

travisamartin · 2026-04-30T22:39:17Z

The file name has two .. for the extension. Should be renamed.

travisamartin

Looks like some includes were added that aren't actually used.

One filename has two .. for the extension and should be renamed.

I had the Tech Writer agent add the requested metadata and do a copy edit on the new and touched files. Since there are a lot of suggested edits, I opened a new PR targeting this one. Take a look: #1905

featrue: F5 dos for nginx 4.9

48bf235

github-actions Bot added documentation Improvements or additions to documentation product/dos Issues related to F5 DoS for NGINX labels Apr 19, 2026

featrue: F5 dos for nginx 4.9

3ee8a41

rnitzan and others added 8 commits April 19, 2026 12:28

featrue: F5 dos for nginx 4.9

84b3230

featrue: F5 dos for nginx 4.9

5e4255f

featrue: F5 dos for nginx 4.9

2ad4496

featrue: F5 dos for nginx 4.9

6324f2b

added Google site verification file for Google Search Console enablem…

ca05e08

…ent (#1871) * added Google site verification file for Google Search Console enablement * moved to /static --------- Co-authored-by: Lam Nguyen <la.nguyen@f5.com>

Add instructions that shows a user how update an existing license (#1874

351d0bb

) * Add instructions that shows a user how update an existing license * Minor change to kubectl param * Correct param

feature: add F5 DoS for NGINX 4.9 release notes

6161d7f

github-actions Bot added product/nic Issues related to NGINX Ingress Controller product/nginx-one-console Issues related to NGINX One Console labels Apr 23, 2026

docs: refine F5 DoS for NGINX 4.9 new features

a54101f

rnitzan marked this pull request as ready for review April 23, 2026 11:03

rnitzan requested a review from a team as a code owner April 23, 2026 11:03

JTorreG reviewed Apr 30, 2026

View reviewed changes

JTorreG requested changes Apr 30, 2026

View reviewed changes

JTorreG changed the title ~~featrue: F5 dos for nginx 4.9~~ feat: F5 dos for nginx 4.9 Apr 30, 2026

mjang requested changes Apr 30, 2026

View reviewed changes

travisamartin added 2 commits April 30, 2026 11:13

docs(nap-dos): fix product names, metadata, and prose quality for 4.9…

dab3055

… release

Revert "docs(nap-dos): fix product names, metadata, and prose quality…

7e96b74

… for 4.9 release" This reverts commit dab3055.

travisamartin mentioned this pull request Apr 30, 2026

NAP DoS 4.9 edit pass #1905

Open

3 tasks

travisamartin reviewed Apr 30, 2026

View reviewed changes

travisamartin requested changes Apr 30, 2026

View reviewed changes


		## Use Helm to install F5 DOS for NGINX

		You will need to edit the `values.yaml` file for a few changes:

	You will need to edit the `values.yaml` file for a few changes:
	To use Helm to install F5 DOS for NGINX you need to edit the `values.yaml` and apply the following changes:


		- Update _appprotectdos.image.repository_ and _appprotectdos.image.tag_ with the image name chosen during when [building the Docker image](#build-the-docker-image).

		The `<JWT Token>` argument should be the _contents_ of the file, not the file itself. Ensure there are no additional characters such as extra whitespace.

	The `<JWT Token>` argument should be the _contents_ of the file, not the file itself. Ensure there are no additional characters such as extra whitespace.
	The `<JWT Token>` argument must be the _contents_ of the file, not the file itself. Ensure there are no additional characters such as extra whitespace.

	Once you have built the image, push it to your private image repository, which should be accessible to your Kubernetes cluster.
	Once you have built the image, push it to your private image repository, which must be accessible to your Kubernetes cluster.


		## Create a Dockerfile

		In the same folder as your credential files, create a _Dockerfile_ based on your desired operating system image using an example from the following sections.

	In the same folder as your credential files, create a _Dockerfile_ based on your desired operating system image using an example from the following sections.
	Create a _Dockerfile_ based on your desired operating system image in the same folder as your credential files using an example from the following sections.


		The `<JWT Token>` argument should be the _contents_ of the file, not the file itself. Ensure there are no additional characters such as extra whitespace.

		On helm deployment environment variables need to be set for image repository and tag.

	On helm deployment environment variables need to be set for image repository and tag.
	On Helm, set the deployment environment variables for image repository and tag.

		`set enviorment variable DOS_IMAGE_REPOSITORY` with your actual nginx-dos image anmae.
		`set enviorment variable DOS_IMAGE_TAG` with your actual nginx-dos image tag.

		@@ -0,0 +1 @@
		google-site-verification: google1f145127a2762dc1.html No newline at end of file


		{{< call-out "note" >}}

		At this stage, you have finished deploying F5 DOS for NGINX and can look at [Post-installation checks](#post-installation-checks).

	At this stage, you have finished deploying F5 DOS for NGINX and can look at [Post-installation checks](#post-installation-checks).
	The deployment of F5 DOS for NGINX is now complete. You can skip to the [Post-installation checks](#post-installation-checks) now.

	## F5 DoS for NGINX Arbitrator
	## F5 DoS for NGINX arbitrator

Conversation

rnitzan commented Apr 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposed changes

Checklist

Footnotes

Uh oh!

github-actions Bot commented Apr 19, 2026

✅ Deploy Preview will be available once build job completes!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JTorreG Apr 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JTorreG left a comment

Choose a reason for hiding this comment

Uh oh!

JTorreG commented Apr 30, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

travisamartin commented Apr 30, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

travisamartin left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

rnitzan commented Apr 19, 2026 •

edited

Loading

JTorreG Apr 30, 2026 •

edited

Loading